System and method for routing an emergency call

ABSTRACT

A method and a system for routing an emergency call to a PSAP [ 322 ]. Upon receiving an emergency call request from at least one user device [ 302 ] at an eNodeB [ 304 ], an ESMLC [ 310 ] computes a current location information of the at least one user device [ 302 ]. Further, a GMLC [ 312 ] identifies a serving cell identifier for the at least one user device [ 302 ] based on the current location. Furthermore, an emergency location platform [ 314 ] identifies at least one PSAP [ 322 ] in a cell site master database [ 316 ] based on the serving cell identifier and extracts one or more parameters for the at least one user device [ 302 ] from a subscriber information database [ 318 ]. Lastly, the emergency location platform [ 314 ] provides at least one of the current location information and the one or more parameters to the identified at least one PSAP [ 322 ] on an access network channel.

TECHNICAL FIELD

The present invention generally relates to Heterogenous Networks(HetNet) and more particularly relates to identifying location of anemergency caller and to route the emergency call to a public-safetyanswering point (PSAP).

BACKGROUND OF THE INVENTION

The following description of related art is intended to providebackground information pertaining to the field of the invention. Thissection may include certain aspects of the art that may be related tovarious features of the present invention. However, it should beappreciated that this section be used only to enhance the understandingof the reader with respect to the present invention, and not asadmissions of prior art.

In a traditional cellular deployment, service operators are nowreinforcing their macro-cells deployment with one or multiple lowpowered small cellular cells (generally termed as Femto/Pico/Microcells) placed at multiple strategic locations within one or more macrocoverage areas. This kind of reinforced cellular network is generallytermed as Heterogeneous Network, in short, HetNet. For a typical HetNet,strategic locations for small cells generally include areas with highdensity of users, such as shopping malls, airports, railway/busstations, colleges, etc. Also, these locations might include areas withdead-spots, or areas with low macro signal strength, such as indoorestablishments or peripheral locations of a macro coverage area. HetNetprovides increased mobile data capacity along with providing bettermobile coverage, thereby enhancing the overall user's mobile broadbandexperience.

Wi-Fi technology has witnessed tremendous growth and commercializationin the recent years. Almost all the available user devices (or userequipment) with cellular capability support also tend to have Wi-Ficapability in order to connect to Wi-Fi networks operating in theunlicensed frequency bands, either 2.4 GHz or 5 GHz. Therefore, thecellular operators are motivated to use ubiquitous and cost-effectiveWi-Fi technology in pursuing the overall HetNet strategy, for instance,deploying low powered Wi-Fi cells along with cellular small cells atmultiple strategic locations identified for a HetNet. Further, for easeof maintenance and provision, few operators are also beginning to useWi-Fi integrated versions of small cellular cells, wherein a Wi-Fi andcellular small cell technology are made available on common equipment.

FIG. 1 illustrates an exemplary block diagram representation of aheterogenous communication network architecture [100]. Referring to FIG.1 illustrates an exemplary block diagram representation of aheterogenous communication network architecture [100], in accordancewith exemplary embodiments of the present invention. As shown in FIG. 1, the heterogenous wireless communication network [100] comprises of amacro base station [101A] wide area overlay mobility coverage, and oneor more micro base station [101B, 101C] further connected to Wi-Fiaccess points [101E, 101F, 101G, 101H, 101I], and a micro base station[101D] with built-in Wi-Fi access point capability.

Telecom service operators today are looking for a green field deploymentto enable any SIM subscribers to make/receive emergency voice & videocalls using any un-trusted/unmanaged WiFi environment (like the VoLTEemergency calls), such that the emergency services can be provided toSIM based subscribers locally over any environment. With the technologygrowing at a tremendous rate, a demand has arisen for emergency alertmechanism for disposal of the consumers during emergency incidentsacross the globe that may pose a threatening environment.

The location information plays a critical role in emergency services,for instance, one purpose of the location information is to enable theIMS network to determine which Public-Safety Answering Point (PSAP)serves the area where the user device is currently located such that theIMS network can route the emergency call to the correct PSAP. A secondpurpose of the location information is for the PSAP to get more accurateor updated location information for the user device during or after theemergency session required by local authorities to ascertain the factsof the emergency incidence. For offering effective emergency assistanceto a distress caller, the authorities have taken an initiative to deploycentralized PSAPs in each state. As part of this initiative, all TSPsare required to establish connectivity with respective state PSAP forproviding the location coordinates of emergency caller. The emergencycalls shall continue to be routed via existing POI connectivity withanchoring TSP. In any country, a mix of 2G, 3G & 4G subscriber alongwith Het-net environment base exists. Due to this, Pan-country IMS basedinterfaces do not exist across service operators.

Traditionally whenever a subscriber dials an Emergency call to a PSAP,the user device location is required by PSAP for the PSAP to serve thesubscriber effectively. In 2G/3G networks, there is no standard basedinterface to provide the location of emergency caller along with hisemergency call to PSAP. However, in 4G technology, the service operatorsends the location of the emergency caller over SIP interface to PSAP aslong as the PSAP has an IMS support. However, in the current scenario,the PSAP does not support IMS interfaces and continue to receiveemergency calls over TDM interface. The PSAPs also continue to receiveemergency calls from the TSPs over TDM interface only. For receivinglocation information, the service operators establish VPN connectivity.Thus, whenever PSAP receives an emergency call, they get the MSISDN ofthe caller. Also, with MNP implementation, the PSAP has to perform MNPdip to get the serving operator details. The PSAP then performs alocation query to serving operator for the emergency calling MSISDN. Theservice operator provides MLP interface for performing the locationquery over established VPN connectivity. This query is served viaservice operator's emergency location servers, which internally queriesrespective GMLC and provides the location to PSAP in response. In thiscall flow, the emergency call and corresponding location query from thePSAP may not be accomplished at the same time instance, and the locationquery often gets delayed due to platform or transport issue. In suchscenarios, the location coordinates provided by the service operatorwith respect to the actual location of emergency caller may vary.Additionally, there can be failures in location query due to subscribernot reachable/switched off or other network issues. Therefore, in viewof the above highlighted and other inherent limitations in the existingsolutions, there exists a need in the art to provide a system and amethod for automatically identifying a location of the emergency callerand to route the emergency call to a PSAP.

SUMMARY

This section is provided to introduce certain objects and aspects of thepresent invention in a simplified form that are further described belowin the detailed description. This summary is not intended to identifythe key features or the scope of the claimed subject matter. In order toovercome at least a few problems associated with the known solutions asprovided in the previous section, an object of the present invention isto provide a system and a method for routing an emergency call to apublic-safety answering point (PSAP). Another object of the presentinvention is to provide a system and a method for providing seamlessemergency services on 3GPP access network to a user device. Yet anotherobject of the present invention is to provide a method and a system forproviding emergency caller location to IMS non-compliant PSAP. Yetanother object of the present invention is to provide a method and asystem for reducing PSAP response time in providing emergency services.Yet another object of the present invention is to provide a method and asystem for routing the emergency call to a serving area PSAP and not tothe home circle PSAP. Yet another object of the present invention is toprovide a method and a system for providing efficient emergency servicesin a cost-effective manner withing the existing deployed EPC Network tocater the huge traffic in heterogeneous network. Yet another object ofthe present invention is to provide a method and a system for providingthe SIM based subscribers to be able to dial in emergency numbers andavail emergency service facility defined by authorities whileregistering.

In order to achieve at least some of the above-mentioned objectives, thepresent invention provides a method and system for routing an emergencycall to a public-safety answering point (PSAP). A first aspect of thepresent invention relates to a method for routing an emergency call to apublic-safety answering point (PSAP). The method comprises receiving,from at least one user device, an emergency call request at an eNodeB.Next, an Evolved Serving Mobile Location Center (ESMLC) computes acurrent location information of the at least one user device based onthe emergency call request. Further, a Gateway Mobile Location Center(GMLC) identifies a serving cell identifier for the at least one userdevice based on the current location. Furthermore, an emergency locationplatform identifies at least one PSAP for the at least one user devicein a cell site master database based on the serving cell identifier.Subsequently, the emergency location platform extracts one or moreparameters for the at least one user device from a subscriberinformation database based on the emergency call request. Lastly, theemergency location platform provides at least one of the currentlocation information and the one or more parameters to the identified atleast one PSAP on an access network channel.

Another aspect of the present invention relates to a method for routingan emergency call to a public-safety answering point (PSAP). The systemcomprises an eNodeB, an Evolved Serving Mobile Location Center (ESMLC),a Gateway Mobile Location Center (GMLC), an emergency location platformand at least one PSAP, all the components connected to each other unlessotherwise indicated and work in conjunction to achieve the objects ofthe present invention. The eNodeB is configured to receive an emergencycall request from at least one user device. The ESMLC is configured tocompute a current location information of the at least one user devicebased on the emergency call request.

The GMLC is configured to identify a serving cell identifier for the atleast one user device based on the current location. The emergencylocation platform is configured to identify at least one PSAP for the atleast one user device in a cell site master database based on theserving cell identifier. The emergency location platform is furtherconfigured to extract one or more parameters for the at least one userdevice from a subscriber information database based on the emergencycall request. The emergency location platform is also configured toprovide at least one of the current location information and the one ormore parameters to the identified at least one PSAP on an access networkchannel.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings, which are incorporated herein, and constitutea part of this disclosure, illustrate exemplary embodiments of thedisclosed methods and systems in which like reference numerals refer tothe same parts throughout the different drawings. Components in thedrawings are not necessarily to scale, emphasis instead being placedupon clearly illustrating the principles of the present disclosure. Somedrawings may indicate the components using block diagrams and may notrepresent the internal circuitry of each component. It will beappreciated by those skilled in the art that disclosure of such drawingsincludes disclosure of electrical components, electronic components orcircuitry commonly used to implement such components.

FIG. 1 illustrates an exemplary heterogenous network architecturediagram.

FIG. 2 illustrates an existing solution for providing location of anemergency caller to a PSAP.

FIG. 3 illustrates an exemplary block diagram of system for routingemergency call to a PSAP, in accordance with exemplary embodiments ofthe present invention.

FIG. 4 illustrates an exemplary high level architecture diagram of aheterogenous network architecture, in accordance with exemplaryembodiments of the present invention.

FIG. 5 illustrates an exemplary logical interface SWu of theheterogenous network architecture, in accordance with exemplaryembodiments of the present invention.

FIG. 6 illustrates an exemplary logical interface SWm of theheterogenous network architecture, in accordance with exemplaryembodiments of the present invention.

FIG. 7 illustrates an exemplary logical interface SWx of theheterogenous network architecture, in accordance with exemplaryembodiments of the present invention.

FIG. 8 illustrates an exemplary logical interface S2b of theheterogenous network architecture, in accordance with exemplaryembodiments of the present invention.

FIG. 9 illustrates an exemplary logical interface S6b of theheterogenous network architecture, in accordance with exemplaryembodiments of the present invention.

FIG. 10 illustrates an exemplary method flow diagram depicting a methodfor routing an emergency call to a PSAP, in accordance with exemplaryembodiments of the present invention.

FIG. 11 illustrates another exemplary block diagram of the system forrouting emergency call to a PSAP, in accordance with exemplaryembodiments of the present invention.

FIG. 12 illustrates an exemplary call flow diagram for routing anemergency call to a PSAP, in accordance with exemplary embodiments ofthe present invention.

FIG. 13 illustrates an exemplary call flow diagram for routing anemergency call to a PSAP, in accordance with exemplary embodiments ofthe present invention.

FIG. 14 illustrates an exemplary implementation of the solution of thepresent invention for VoWiFi users in the Heterogeneous Network, inaccordance with exemplary embodiments of the present invention.

The foregoing shall be more apparent from the following more detaileddescription of the disclosure.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofembodiments of the invention. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive.

The ensuing description provides exemplary embodiments only, and is notintended to limit the scope, applicability, or configuration of thedisclosure. Rather, the ensuing description of the exemplary embodimentswill provide those skilled in the art with an enabling description forimplementing an exemplary embodiment. It should be understood thatvarious changes may be made in the function and arrangement of elementswithout departing from the spirit and scope of the invention as setforth.

Specific details are given in the following description to provide athorough understanding of the embodiments. However, it will beunderstood by one of ordinary skill in the art that the embodiments maybe practiced without these specific details. For example, circuits,systems, networks, processes, and other components may be shown ascomponents in block diagram form in order not to obscure the embodimentsin unnecessary detail. In other instances, well-known circuits,processes, algorithms, structures, and techniques may be shown withoutunnecessary detail in order to avoid obscuring the embodiments.

Also, it is noted that individual embodiments may be described as aprocess which is depicted as a flowchart, a flow diagram, a sequencediagram, a data flow diagram, a structure diagram, or a block diagram.Although a flowchart may describe the operations as a sequentialprocess, many of the operations can be performed in parallel orconcurrently. In addition, the order of the operations may bere-arranged. A process is terminated when its operations are completedbut could have additional steps not included in a figure. A process maycorrespond to a method, a function, a procedure, a subroutine, asubprogram, etc. When a process corresponds to a function, itstermination can correspond to a return of the function to the callingfunction or the main function.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks (e.g., a computer-program product) may be stored in amachine-readable medium. A processor(s) may perform the necessarytasks.’

The word “exemplary” and/or “demonstrative” is used herein to meanserving as an example, instance, or illustration. For the avoidance ofdoubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art. Furthermore, to the extent that theterms “includes,” “has,” “contains,” and other similar words are used ineither the detailed description or the claims, such terms are intendedto be inclusive-in a manner similar to the term “comprising” as an opentransition word-without precluding any additional or other elements.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, theappearances of the phrases “in one embodiment” or “in an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof. As used herein, the term “and/or”includes any and all combinations of one or more of the associatedlisted items.

As utilized herein, terms “component,” “system,” “platform,” “node,”“layer,” “selector,” “interface,” and the like are intended to refer toa computer-related entity, hardware, software (e.g., in execution),and/or firmware. For example, a component can be a process running on aprocessor, a processor, an object, an executable, a program, a storagedevice, and/or a computer. By way of illustration, an applicationrunning on a server and the server can be a component. One or morecomponents can reside within a process and a component can be localizedon one computer and/or distributed between two or more computers.

Moreover, terms like “source and/or destination user device (UE)”,“mobile station”, “smart computing device”, “user device”, “userdevice”, “device”, “smart mobile communications device”, “mobilecommunication device”, “mobile device”, “mobile subscriber station,”“access terminal,” “terminal,” “handset,” “originating device,”“terminating device,” and similar terminology refers to any electrical,electronic, electro-mechanical computing device or equipment or acombination of one or more of the above devices. Smart computing devicesmay include, but not limited to, a mobile phone, smartphone, virtualreality (VR) devices, augmented reality (AR) devices, pager, laptop, ageneral-purpose computer, desktop, personal digital assistant, tabletcomputer, mainframe computer, or any other computing device as may beobvious to a person skilled in the art. In general, a smart computingdevice is a digital, user-configured, computer networked device that canbe operated autonomously. A smart computing device is one of theappropriate systems for storing data and other private/sensitiveinformation. The smart computing device operates at all the seven levelsof ISO reference model, but the primary function is related to theapplication layer along with the network, session and presentationlayer. The smart computing device may also have additional features of atouch screen, apps ecosystem, physical and biometric security, etc.Further, a ‘smartphone’ is one type of “smart computing device” thatrefers to the mobility wireless cellular connectivity device that allowsend users to use services on cellular networks such as including but notlimited to 2G, 3G, 4G, 5G and/or the like mobile broadband internetconnections with an advanced mobile operating system which combinesfeatures of a personal computer operating system with other featuresuseful for mobile or handheld use. These smartphones can access theInternet, have a touchscreen user interface, can run third-party appsincluding capability of hosting online applications, music players andare camera phones possessing high-speed mobile broadband 4G LTE internetwith video calling, hotspot functionality, motion sensors, mobilepayment mechanisms and enhanced security features with alarm and alertin emergencies. Mobility devices may include smartphones, wearabledevices, smart-watches, smart bands, wearable augmented devices, etc.For the sake of specificity, the mobility device is referred to bothfeature phone and smartphones in present disclosure but does not limitthe scope of the disclosure and may extend to any mobility device inimplementing the technical solutions. The above smart devices includingthe smartphone as well as the feature phone including IoT devices enablethe communication on the devices. Further, the foregoing terms areutilized interchangeably in the subject specification and relateddrawings.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“owner,” and the like are employed interchangeably throughout thesubject specification and related drawings, unless context warrantsparticular distinction(s) among the terms. It should be appreciated thatsuch terms can refer to human entities, or automated componentssupported through artificial intelligence, e.g., a capacity to makeinference based on complex mathematical formulations, that can providesimulated vision, sound recognition, decision making, etc. In addition,the terms “wireless network” and “network” are used interchangeable inthe subject application, unless context warrants particulardistinction(s) among the terms.

As used herein, a “processor” or “processing unit” includes one or moreprocessors, wherein processor refers to any logic circuitry forprocessing instructions. A processor may be a general-purpose processor,a special-purpose processor, a conventional processor, a digital signalprocessor, a plurality of microprocessors, one or more microprocessorsin association with a DSP core, a controller, a microcontroller, alow-end microcontroller, Application Specific Integrated Circuits, FieldProgrammable Gate Array circuits, any other type of integrated circuits,etc. The processor may perform signal coding data processing,input/output processing, and/or any other functionality that enables theworking of the system according to the present disclosure. Morespecifically, the processor or processing unit is a hardware processor.

Referring to FIG. 2 illustrates an existing solution for providinglocation of an emergency caller to a PSAP [212]. The PSAP [212]establishes a POI with an aggregator TSP [210] from which all emergencycalls are received and routed. Once the call is received by the PSAP[212] emergency center executive, the PSAP [212] performs an MNP dip toidentify the home operator of the emergency caller. The PSAP [212]initiates a MT location query to operator over VPN connectivity. In caseof IP network TSP, this is a standard MLP request as defined in 3GPPspecifications. The TSPs [204] have deployed Emergency LocationPlatforms [208], which receives these location requests from PSAPs [212]over MLP, interface. The Emergency Location Platforms [208] then queriesthe GMLC [206] to get the location coordinates. The GMLC [206] usingstandard MT location query protocol gets the location of the givenIMSI/MSISDN by using location methods like AGPS, OTDOA, UL-ECID or CellID. This is then routed back to PSAP [212] by the Emergency LocationPlatform [208]. The PSAP [212] then plots this on the screen of theexecutive who is able to view it on map and address the emergency callalong. Additionally, the PSAP [212] also extracts the subscriber relatedinformation from their local subscriber database, which is receivedperiodically from all TSPs [204]. However, it has been observed that thetime instance of receiving an emergency call and requesting location mayhave latency due to system or network issues in the existing solution,thus, leading to failure in location query as well as deviation betweenthe received location coordinates versus the actual location of theemergency caller. Also, the subscriber information, which isperiodically shared with PSAP [212] by TSPs [204] may not be the latestupdated one. The PSAP needs to query separate subscriber database andpull this information for each emergency call.

Thus, in order to resolve the above highlighted and other inherentlimitations in the existing solutions, the present invention provides asystem and a method for automatically identifying a location of theemergency caller and to route the emergency call to a PSAP. The solutionof the present invention provides that upon receiving an emergency callfrom a user device, a current location of the user device is determined.Based on the current location of the user device, a serving cellidentifier is detected, and a PSAP associated with serving cellidentifier is selected. Furthermore, a subscriber information associatedwith the user device is obtained from a subscriber database.Accordingly, the current location and the subscriber information for theuser device along with the emergency call transmitted to the PSAP.

Hereinafter, exemplary embodiments of the present disclosure will bedescribed in detail with reference to the accompanying drawings so thatthose skilled in the art can easily carry out the present disclosure.

Referring to FIG. 3 illustrates an exemplary block diagram of system forrouting emergency call to a PSAP, in accordance with exemplaryembodiments of the present invention. The system comprises at least oneuser device [302], an eNodeB [304], an Evolved Serving Mobile LocationCenter (ESMLC) [310], a Gateway Mobile Location Center (GMLC) [312], anemergency location platform [314] and at least one PSAP [322], all thecomponents connected to each other in a heterogenous network unlessotherwise indicated and work in conjunction to achieve the objects ofthe present invention. In an instance of the present invention, theheterogenous network may be a wired network, a wireless network, or acombination thereof. The heterogenous network may be a single network ora combination of two or more networks.

The eNodeB [304] is configured to receive an emergency call request fromat least one user device [302]. The present invention encompasses that,in an instance, the emergency call request comprises one of an emergencyAPN, an IMSI and a MSISDN. The present invention encompasses that the atleast one user device [302] is attached to the eNodeB [304] on anon-access network channel, and the emergency call is transmitted by theat least one user device [302] to the eNodeB [304] on a SWu interface.For example, whenever a user dials an emergency number for example, 112,etc. the user device [302] initiates an emergency APN. As soon as theeNodeB [304] receives the emergency call, it initiates a locationcomputation request (MO location) for the user device [302] to the ESMLC[310] based on the emergency APN in the emergency call request. In aninstance of the present invention, the emergency call request isreceived at a Mobile Management Entity (MME), and the MME initiates thelocation computation request (MO location) to the ESMLC [310].

The present invention also encompasses that the eNodeB [304] is furtherconfigured to continuously receive a logging information from the atleast one user device [302]. The logging information comprises ofdetails of the at least one user device [302] including but not limitedto a time of a logging event, a location of the at least one user device[302], at least one audio input of sound from a mic of the at least oneuser device [302], at least one visual input of a surrounding from acamera of the at least one user device [302], at least one measurementdata from one or more sensors of the at least one user device [302]. TheeNodeB [304] if further configured to automatically push at least oneadvertisement on the at least one user device [302] based on the logginginformation. For example, basis a time and a location of the at leastone user device [302], the eNobeB [304] pushes information aboutcritical services such as ambulance service providers, hospitals,medical stores, any ancillary emergency needs situated near the receivedlocation of the at least one user device [302]. In another example,basis the at least one visual input, the eNodeB [304] pushes informationabout critical service, say, an ambulance service providers, hospitals,medical stores, fire services, any ancillary emergency needs, etc. basedon an analysis of the at least one visual input.

The present invention further encompasses that the emergency locationplatform [314] is configured to transmit a request for sharing locationto one or more other devices associated with the one or more emergencycontacts. In response to said request, the emergency location platform[314] receives locations from the one or more other devices of the oneor more emergency contacts. The emergency location platform [314] isalso configured to determine at least one other device from the one ormore other devices in a close proximity to the at least one user device[302] based on a comparison of the locations of the one or more devicesand the current location information of the at least one user device. Inanother instance, the present invention encompasses that the emergencylocation platform [314] determines the at least one other device fromthe one or more other devices in a close proximity to the at least oneuser device [302] based on a comparison of the locations of the one ormore devices and the logging information received from the at least oneuser device. The emergency location platform [314] is also configured totransmit an emergency notification to the at least one other device,wherein the emergency notification further comprises of the currentlocation information of the at least one user device by. For example, auser enlists at least a brother and a sister as one or more emergencycontacts, the emergency location platform [314] requests the locationfrom the devices of the brother and the sister. The emergency locationplatform [314] determines at least one of the one or more emergencycontacts in close proximity of the location of the user device [302] andsends an emergency notification to the other device of the one or moreemergency contacts.

The ESMLC [310] is configured to receive a location computation requestfrom the eNodeB [304]. The ESMLC [310] is configured to compute acurrent location information of the at least one user device [302] basedon the emergency call request. The present invention encompasses thatthe ESMLC [310] is configured to compute the current locationinformation of the at least one user device [302] based on one ofAssisted-GPS AGPS, Observed Time Difference of Arrival (OTDOA) andEnhanced Cell ID (UL-ECID). The present invention encompasses that thecurrent location information comprises of a latitude information, alongitude information, a SIM identifier and a transaction ID. The ESMLC[310] is further configured to provide the current location informationto the GMLC [312] and the emergency location platform [314]. In anotherinstance, the present invention encompasses that the ESMLC [310]provides the current location information to the MME which furtherprovides the current location information to the GMLC [312].

The GMLC [312] is configured to identify a serving cell identifier forthe at least one user device [302] based on the current location. TheGMLC [312] is further configured to provide the serving cell identifierto the emergency location platform [314]. In another instance, thepresent invention encompasses that the GMLC [312] and the ESMLC [310]coexist as one entity, and accordingly the singular entity GMLC[312]/ESMCL [310] is configured to provide the independent working ofthe GMLC [312] and ESMLC [310]. Thus, the GMLC [312]/ESMLC [310] isconfigured to provide the current location information and the servingcell identifier to the emergency location platform [314].

The emergency location platform [314] is configured to receive at leastone of the current location information and the serving cell identifierfrom one of the GMLC [312] and the ESMLC [310]. The emergency locationplatform [314] is configured to identify at least one PSAP [322] for theat least one user device [302] in a cell site master database [316]based on the serving cell identifier. The present invention encompassesthat the cell site master database [316] comprises of a correlation of aplurality of cell identifiers with at least one city and at least onePSAP [322]. In an instance, the present invention encompasses that theemergency location platform [314] is configured to identify a servingcity based on a comparison of the identified serving cell with theplurality of cell identifiers, and to determine the at least one PSAP[322] associated with the identified serving city based on a successfulmatch in the cell site master database [316]. Table 1 below illustratesan exemplary cell site master database [316]. As shown in the Table 1below, a given PSAP [322] is mapped against each city, wherein the PSAP[322] is configured to provide the emergency services.

Deliv- Circle State PSAP ery Cell_ID SAP_ID City Code Code [322] Mode405863290135 I-MP- Damoh MP MP PSAP XML DMOH- [322]-1: ENB-7084 MP100PSAP XML [322]-2: Bhopal Police 405863508535 I-MP- Manora MP CG PSAP XMLMANO- [322]-1: ENB-9001 CG100

The emergency location platform [314] is further configured to extractone or more parameters for the at least one user device [302] from asubscriber information database [318] based on the emergency callrequest. The present invention encompasses that the subscriberinformation database [318] comprises of a correlation of one or moreMSISDNs with one or more parameters. In an instance, the presentinvention encompasses that extracting the one or more parameters for theat least one user device [302] is based on a comparison of the MSISDNwith the one or more MSISDNs. The present invention encompasses that theone or more parameters comprises of a name, an age, a gender, anaddress, an one or more emergency contacts and a relative's name. Table2 below illustrates an exemplary subscriber information database [318].

Data type/ SI No Parameter Allowed Values Description Remarks 1 mobileNoLong SIM Number Location Info 2. latitude double Current latitudeLocation Info 3. longitude double Current Longitude Location Info 4.callerName String Name of Caller SDR Info 5. callerAddress StringAddress SDR Info 6 callerState String State SDR Info 7. age Integer AgeSDR Info 8. gender String Gender SDR Info 9 alternateNo Long AlternateContact SDR Info No 10. FATHER_HUSBAND_NAME String Name of Caller's SDRInfo Father/Husband 11. Trans id/Trace id Long Transaction ID LocationInfo

The emergency location platform [314] is also configured to provide atleast one of the current location information and the one or moreparameters to the identified at least one PSAP [322] on an accessnetwork channel. The present invention encompasses that the currentlocation information and the one or more parameters are combined togenerate a https message and said https message is provided to theidentified at least one PSAP [322]. The emergency location platform[314] is also configured to route the emergency call to the identifiedat least one PSAP [322].

The at least one PSAP [322] is also configured to receive at least oneof the current location information and the one or more parameters fromthe emergency location platform [314]. In another instance, the presentinvention encompasses that the at least one PSAP [322] is alsoconfigured to receive the emergency call from the emergency locationplatform [314]. With availability of the received information at thePSAP [322], an executive at the PSAP [322] will be able to seamlesslyview the location of the user device [302] from where the emergency calloriginated as well as the personal information of the user of the userdevice [302] while handling the emergency call.

In another instance of the present invention, the at least one PSAP[322] is also configured to transmit a location request for the at leastone user device [302] to the emergency location platform [314]. The atleast one PSAP [322] is configured to transmit the location request forthe at least one user device [302] in an event of a failure to receivethe current location information of the at least one user device [302].The at least one PSAP [322] is also configured to transmit the locationrequest for the at least one user device [302] in order to retrieve thecurrent location of the at least one user device [302], say if there's achange in location of the user device [302]. The emergency locationplatform [314] is configured to transmit the request for location of theat least one user device [302] to the ESMLC [310]. The ESMLC [310] isfurther configured to recompute the updated location information of theat least one user device [302]. The emergency location platform [314] isfurther configured to extract the one or more parameters for the atleast one user device [302] from the subscriber information database[318] based on the emergency call request. The emergency locationplatform [314] is further configured to provide at least one of theupdated location information and the one or more parameters to theidentified at least one PSAP [322].

Referring to FIG. 4 illustrates an exemplary high level architecturediagram of a heterogenous network architecture, in accordance withexemplary embodiments of the present invention. The heterogenous networkarchitecture comprises of a Signalling Gateway Function (SGW) [402], aHome Subscriber Server (HSS) [410], a Policy and Charging Rules Function(PCRF) [406], a Packet data Network Gateway (PDN-GW or PGW) [404], anEvolved Packet Data Gateway (ePDG) [414], anAuthentication-Authorization-Accounting (AAA) server [412] and an IPMultimedia Core Network Subsystem (IMS) network [408], said componentsare connected via logical interfaces as also indicated in FIG. 4 , andas explained below. In another instance, the present inventionencompasses that the GMLC [312] is integrated with the HSS [410]. Inanother instance, the present invention encompasses the emergencylocation platform [112] is located outside the core network.

Referring to FIG. 5 illustrates an exemplary logical interface SWu ofthe heterogenous network architecture, in accordance with exemplaryembodiments of the present invention. SWu is a secure interface betweenan IPSec client (e.g., a user device [302]) and the ePDG [414] in anon-3GPP access network, say an untrusted and unmanaged network. The SWuinterface carries IPSec tunnels. The IKEv2 protocol is used to establishIPSec tunnels between the user devices [302] and ePDG [414].

Referring to FIG. 6 illustrates an exemplary logical interface SWm ofthe heterogenous network architecture, in accordance with exemplaryembodiments of the present invention. SWm is the interface used toconnect to the ePDG [414] with the AAA server [412]. It is used totransport mobility parameters for the connected IPSec clients (e.g.,user devices [302]) and the tunnel's authentication and authorizationdata using EAP-AKA method.

Referring to FIG. 7 illustrates an exemplary logical interface SWx ofthe heterogenous network architecture, in accordance with exemplaryembodiments of the present invention. SWx is the interface used toconnect the AAA server [412] to the HSS [410]. It is used to transportmobility parameters of the IPSec clients (e.g., user devices [302]) andfetch user authorization data.

Referring to FIG. 8 illustrates an exemplary logical interface S2b ofthe heterogenous network architecture, in accordance with exemplaryembodiments of the present invention. S2b is the interface used toconnect the PGW [404] to the IMS network [408]. It is based on GTPv2protocol and used to establish WLAN sessions for the IPSec clients(e.g., user device [302]).

Referring to FIG. 9 illustrates an exemplary logical interface S6b ofthe heterogenous network architecture, in accordance with exemplaryembodiments of the present invention. S6b is the interface used toconnect the AAA server [412] to the PGW [404]. It is used to update thePGW [404] address to the HSS [410], when the IPSec client (e.g., userdevice [302]) is attached on non-3GPP access.

Referring to FIG. 10 illustrates an exemplary method flow diagramdepicting a method for routing an emergency call to a PSAP [322], inaccordance with exemplary embodiments of the present invention. Themethod starts at step [1002]. At step [1004], receiving an emergencycall request from the at least one user device [302] at an eNodeB [304].The present invention encompasses that the emergency call requestcomprises one of an emergency APN, an IMSI and a MSISDN. The presentinvention encompasses that the at least one user device [302] isattached to the eNodeB [304] on a non-access network channel, and theemergency call is transmitted by the at least one user device [302] tothe eNodeB [304] on a SWu interface. For example, whenever a user dialsan emergency number for example, 112, etc. the user device [302]initiates an emergency APN. As soon as the eNodeB [304] receives theemergency call, it initiates a location computation request (MOlocation) for the user device [302] to the ESMLC [310] based on theemergency APN in the emergency call request. In an instance of thepresent invention, the emergency call request is received at a MobileManagement Entity (MME), and the MME initiates the location computationrequest (MO location) to the ESMLC [310].

At step [1006], the ESMLC [310] computes a current location informationof the at least one user device [302] based on the emergency callrequest. The present invention encompasses that the ESMLC [310] isconfigured to compute the current location information of the at leastone user device [302] based on one of Assisted-GPS AGPS, Observed TimeDifference of Arrival (OTDOA) and Enhanced Cell ID (UL-ECID). Thepresent invention encompasses that the current location informationcomprises of a latitude information, a longitude information, a SIMidentifier and a transaction ID. The ESMLC [310] provides the currentlocation information to the GMLC [312] and the emergency locationplatform [314]. In another instance, the present invention encompassesthat the ESMLC [310] provides the current location information to theMME which further provides the current location information to the GMLC[312].

At step [1008], the GMLC [312] identifies a serving cell identifier forthe at least one user device [302] based on the current location. TheGMLC [312] is provides the serving cell identifier to the emergencylocation platform [314]. Next, at step [1010], the emergency locationplatform [314] identifies at least one PSAP [322] for the at least oneuser device [302] in a cell site master database [316] based on theserving cell identifier. The present invention encompasses that the cellsite master database [316] comprises of a correlation of a plurality ofcell identifiers with at least one city and at least one PSAP [322]. Inan instance, the present invention encompasses that the emergencylocation platform [314] is configured to identify a serving city basedon a comparison of the identified serving cell with the plurality ofcell identifiers, and to determine the at least one PSAP [322]associated with the identified serving city based on a successful matchin the cell site master database [316]. Table 1 below illustrates anexemplary cell site master database [316]. As shown in the Table 1below, a given PSAP [322] is mapped against each city, wherein the PSAP[322] is configured to provide the emergency services.

Deliv- Circle State PSAP ery Cell_ID SAP_ID City Code Code [322] Mode405863290135 I-MP- Damoh MP MP PSAP XML DMOH- [322]-1: ENB-7084 MP100PSAP XML [322]-2: Bhopal Police 405863508535 I-MP- Manora MP CG PSAP XMLMANO- [322]-1: ENB-9001 CG100

Subsequently, at step [1012], the emergency location platform [314]extracts one or more parameters for the at least one user device [302]from a subscriber information database [318] based on the emergency callrequest. The present invention encompasses that the subscriberinformation database [318] comprises of a correlation of one or moreMSISDNs with one or more parameters and extracting the one or moreparameters for the at least one user device [302] is based on acomparison of the MSISDN with the one or more MSISDNs. The presentinvention encompasses that the one or more parameters comprises of aname, an age, a gender, an address, an one or more emergency contactsand a relative's name. Table 2 below illustrates an exemplary subscriberinformation database [318].

Data type/ SI No Parameter Allowed Values Description Remarks 1.mobileNo Long SIM Number Location Info 2. latitude double Currentlatitude Location Info 3. longitude double Current Longitude LocationInfo 4 callerName String Name of Caller SDR Info 5. callerAddress StringAddress SDR Info 6. callerState String State SDR Info 7. age Integer AgeSDR Info 8. gender String Gender SDR Info 9 alternateNo Long AlternateContact SDR Info No 10. FATHER_HUSBAND_NAME String Name of Caller's SDRInfo Father/Husband/ Emergency Caller 11. Trans id/Trace id LongTransaction ID Location Info

At step [1014], the emergency location platform [314] provides at leastone of the current location information and the one or more parametersto the identified at least one PSAP on an access network channel. Thepresent invention encompasses that the current location information andthe one or more parameters are combined to generate a https message andsaid https message is provided to the identified at least one PSAP[322]. The emergency location platform [314] is also configured to routethe emergency call to the identified at least one PSAP [322]. The methodcompletes at step [1016].

The method of the present invention encompasses that the at least onePSAP [322] receives at least one of the current location information andthe one or more parameters from the emergency location platform [314].In another instance, the present invention encompasses that the at leastone PSAP [322] is also configured to receive the emergency call from theemergency location platform [314].

The method of the present invention further encompasses transmitting, bythe identified at least one PSAP [322], a location request for the atleast one user device [302] to the emergency location platform [314].Next, the ESMLC [310] recomputing the updated location information ofthe at least one user device [302]. Subsequently, the emergency locationplatform [314] extracts the one or more parameters for the at least oneuser device [302] from the subscriber information database [318] basedon the emergency call request (e.g., MSISDN). Lastly, the emergencylocation platform [314] provides at least one of the updated locationinformation and the one or more parameters to the identified at leastone PSAP [322].

The method of the present invention also encompasses that continuouslyreceiving, at the eNodeB [304], a logging information from the at leastone user device [302]. In an instance, the logging information comprisesof details of the at least one user device [302] including but notlimited to a time of a logging event, a location of the at least oneuser device [302], at least one audio input of sound from a mic of theat least one user device [302], at least one visual input of asurrounding from a camera of the at least one user device [302], atleast one measurement data from one or more sensors of the at least oneuser device [302]. The method further comprises automatically pushing,by the eNodeB [304], at least one critical service information on the atleast one user device [302] based on the logging information. Forexample, basis a time and a location of the at least one user device[302], the eNobeB [304] pushes information about critical services suchas ambulance service providers, hospitals, medical stores, notifying oneor more emergency contacts, any other ancillary emergency needs situatednear the received location of the at least one user device [302]. Inanother example, basis the at least one visual input, the eNodeB [304]pushes an information about critical services, say, ambulance serviceproviders, hospitals, medical stores, any ancillary emergency needs,fire brigade, etc. based on an analysis of the at least one visualinput.

The method of the present invention further encompasses transmitting, bythe emergency location platform [314], a request for sharing location toone or more other devices associated with the one or more emergencycontacts. In response to said request, the emergency location platform[314] receives locations from the one or more other devices of the oneor more emergency contacts. Subsequently, the emergency locationplatform [314] determines at least one other device from the one or moreother devices in a close proximity to the at least one user device [302]based on a comparison of the locations of the one or more devices andthe current location information of the at least one user device. Inanother instance, the present invention encompasses that the emergencylocation platform [314] determines the at least one other device fromthe one or more other devices in a close proximity to the at least oneuser device [302] based on a comparison of the locations of the one ormore devices and the logging information received from the at least oneuser device. Thereafter, the emergency location platform [314] transmitsan emergency notification to the at least one other device, wherein theemergency notification further comprises of the current locationinformation of the at least one user device by. For example, a userenlists at least a brother and a sister as one or more emergencycontacts, the emergency location platform [314] requests the locationfrom the devices of the brother and the sister. The emergency locationplatform [314] determines at least one of the one or more emergencycontacts in close proximity of the location of the user device [302],and sends an emergency notification to the other device of the one ormore emergency contacts.

Referring to FIG. 11 illustrates another exemplary block diagram of thesystem for routing emergency call to a PSAP [322], in accordance withexemplary embodiments of the present invention. In scenarios where dueto technical limitations if the current location of the at least oneuser device [302] could not be received at the at least one identifiedPSAP [322], or in scenarios where the PSAP [322] needs to retrieve thecurrent location of the at least one user device [302], the at least oneidentified PSAP [322] sends a location query to the emergency locationplatform [314]. The emergency location platform [314] instructs theESMLC [310] to recompute the location of the at least one user device[302]. The present invention encompasses that the ESMLC [310] isrecomputes the current location information of the at least one userdevice [302] based on one of Assisted-GPS AGPS, Observed Time Differenceof Arrival (OTDOA) and Enhanced Cell ID (UL-ECID). The ESMLC [310]transmits the computed current location of the at least one user device[302] to the emergency location platform [314]. Subsequently, theemergency location platform [314] extracts the one or more parametersfor the at least one user device [302] from the subscriber informationdatabase [318] based on the emergency call request (e.g., MSISDN) of theat least user device [302]. Lastly, the emergency location platform[314] provides at least one of the updated location information and theone or more parameters to the identified at least one PSAP [322].

Referring to FIG. 12 illustrates an exemplary call flow diagram forrouting an emergency call to a PSAP [322], in accordance with exemplaryembodiments of the present invention. At step [1202], whenever a userdials an emergency number for example, 112, etc. the user device [302]initiates an emergency APN. As soon as the eNodeB [304] receives theemergency call, at step [1204], a Mobile Management Entity (MME)initiates the location computation request (MO location) to the ESMLC[310] based on the emergency APN in the emergency call request. At step[1206], the ESMLC [310] computes the current location information of theat least one user device [302] based on one of Assisted-GPS AGPS,Observed Time Difference of Arrival (OTDOA) and Enhanced Cell ID(UL-ECID).

The computed location is provided by the ESMLC [310] to the MME, whichfurther sends the computed location to the GMLC [312]. The GMLC [312]identifies a serving cell identifier for the at least one user device[302] based on the current location. The MME sends the computed locationand the serving cell identifier to the emergency location platform[314]. At step [1208], the emergency location platform [314] identifiesat least one PSAP [322] for the at least one user device [302] in a cellsite master database [316] based on the serving cell identifier. At step[1210], the emergency location platform [314] extracts one or moreparameters for the at least one user device [302] from a subscriberinformation database [318] based on the emergency call request (e.g.,MSISDN. At step [1212], the emergency location platform [314] providesat least one of the current location information and the one or moreparameters to the identified at least one PSAP [322] on an accessnetwork channel. At step [1214], with availability of the receivedinformation at the at least one PSAP [322], an executive at the PSAP[322] will be able to seamlessly view the location of the user device[302] from where the emergency call originated as well as the personalinformation of the user of the user device [302] while handling theemergency call.

Referring to FIG. 13 illustrates an exemplary call flow diagram forrouting an emergency call to a PSAP [322], in accordance with exemplaryembodiments of the present invention. At step [1302], whenever asubscriber dials an emergency number (like 112), an emergency call getsrouted towards a serving PSAP [322] via an aggregating TSP [320] inaccordance with procedure of FIG. 12 . At step [1304], due to any of thetechnical reasons or if there is a need to fetch location of theemergency caller, the PSAP [322] performs MNP DIP to find the servingTSP [306]. At step [1306], the PSAP [322] initiates a location querytowards the identified TSP. At step [1308], the emergency locationplatform [314] queries the GMLC [312] for the location, and the GLMCcomputes the location and provides the location coordinate to theemergency location platform [314] at step [1310]. At step [1312], theemergency location platform [314] queries the cell site database toextract the cell identifier of the serving cell. At step [1314], theemergency location platform [314] queries the subscriber informationdatabase [318] to extract the SDR information for the at least one userdevice [302]. At step [1316], the location coordinates along with theSDR information is composed as a single message and sent as https POSTto the requesting PSAP [322] along with the location response. At step[1318], with availability of the received information at the at leastone PSAP [322], an executive at the PSAP [322] will be able toseamlessly view the location of the user device [302] from where theemergency call originated as well as the personal information of theuser of the user device [302] while handling the emergency call.

Referring to FIG. 14 illustrates an exemplary implementation of thesolution of the present invention for Voice-over-Wi-Fi (VoWiFi) users inthe Heterogeneous Network, in accordance with exemplary embodiments ofthe present invention. The scheme of the exemplary implementationcomprises of the PGW [404], the PCRF [406] and the Proxy-Call SessionControl Function (P-CSCF [416]). At [1402], the P-CSCF [416] sends anAAR message to the PCRF [406] to establish a dedicated bearer for thevoice media stream. The AAR message contains the subscriber ID, AF ID,IMS application layer charging ID, and media information (including themedia type and media stream description). At [1404], the PCRF [406]sends an RAR message containing the PCC rule to the PGW [404]. The PGW[404] searches for the dedicated bearer based on QCI or ARP in the PCCrule. If no dedicated bearer is found, the PGW [404] creates a dedicatedbearer, installs the voice media stream information and the PCC rule inthe dedicated bearer, and sends an RAA message to the PCRF [406] at step[1406]. At [1408], the PCRF [406] sends an AAA message to the P-CSCF[416] to indicate that the dedicated bearer is successfully created forthe voice media stream. At step [1410], the PGW [404] sends a CCR-Umessage to the PCRF [406] notifying that the policy charging that theresource is successfully reserved. At step [1412], the PCRF [406] sendsa CCA-U message to the PGW [404]. At step [1414], the PCRF [406] sendsan RAR message to the P-CSCF [416] indicating that the resource issuccessfully reserved. At step [1416], the P-CSCF [416] sends an RAAmessage to the PGW [404].

The present invention also encompasses that the system and the method ofthe present invention is further provisioned to select (or modify) amode of collection of location and sensor information from the userdevice [302] wherein the mode of collection is one of a continuouslogging mode and a frequent logging mode. In an instance, the presentinvention encompasses that the logging information collected from the atleast one user device is also sent to a cloud server of the eNodeB [304]triggering a cloud module system which sends the collected informationafter every fixed interval to the cloud and everyone in the emergencylist.

The present invention further encompasses that the system and methodprovide for routing the locations details of an emergency caller, i.e.,the user device [302] to a predefined one or more emergency contactsdetails as provisioned in the emergency location platform [314]. Inanother instance the present invention encompasses that the system andthe method is used by law enforcement agencies (LEA) for extracting thelocation and/or SDR details of any mobility subscriber, thus, withappropriate scheduler in the emergency location platform [314], thelocation information is periodically transmitted to the LEAs. In yetanother instance the present invention encompasses that the system andthe method provide a collaborative platform and option to choose the“one or more emergency contacts closest person” that allows everysubscriber on the list to share their location information when thesystem is triggered on any one device. This information is used bysenders' device to auto-sequence the list based on who is closest to thesender smartphone/device. Also, again the system ensures that all deviceor smartphones are not alerted simultaneously to avoid deadlock. Therecipient smartphone sends location discreetly only in emergencysituation for privacy reasons.

The novel solution of the present invention provides a system and amethod for routing an emergency call to a public-safety answering point(PSAP [322]) to provides seamless emergency services on 3GPP accessnetwork to a user device [302] by a IMS non-compliant PSAP [322]. Thesolution of the present invention significantly reduces the PSAP [322]response time in providing emergency services to the emergency caller byrouting the emergency call to a serving area PSAP [322] and not to thehome circle PSAP [322] within the existing deployed EPC Network. Thus,the present invention enables the SIM based subscribers to dial inemergency numbers and avail emergency service facility defined byauthorities while registering.

While considerable emphasis has been placed herein on the preferredembodiments, it will be appreciated that many embodiments can be madeand that many changes can be made in the preferred embodiments withoutdeparting from the principles of the invention. These and other changesin the preferred embodiments of the invention will be apparent to thoseskilled in the art from the invention herein, whereby it is to bedistinctly understood that the foregoing descriptive matter to beimplemented merely as illustrative of the invention and not aslimitation.

1-26. (canceled)
 27. A method for routing a call in a communicationnetwork, the method comprising: receiving, from a user device, a call;determining a current location information of the user device based onthe call; identifying a Public-Safety Answering Point (PSAP)corresponding to the current location information of the user device;and routing the call to the identified PSAP.
 28. The method of claim 27,wherein identifying the PSAP corresponding to the current locationinformation of the user device further comprises: identifying a servingcell identifier for the user device based on the current locationinformation of the user device; and selecting, in a cell site masterdatabase, the PSAP associated with the identified serving cellidentifier.
 29. The method of claim 28, further comprising: obtaining,from a subscriber information database, one or more parameters ofsubscriber information associated with the user device; andtransmitting, to the PSAP, the current location information and the oneor more parameters of the subscriber information.
 30. The method ofclaim 29, further comprising: receiving, from the PSAP, a locationrequest for the user device; redetermining the current locationinformation of the user device; obtaining, from the subscriberinformation database, one or more additional parameters of thesubscriber information associated with the user device; andtransmitting, to the PSAP, redetermined current location information andthe one or more additional parameters.
 31. The method of claim 28,wherein the cell site master database comprises a correlation of aplurality of cell identifiers with one or more cities and one or morePSAPs, and selecting the PSAP associated with the identified servingcell identifier further comprises: identifying a serving city based on acomparison of the identified serving cell identifier with the pluralityof cell identifiers; and determining the PSAP that is associated withthe identified serving city.
 32. The method of claim 27, wherein the oneor more parameters of the subscriber information associated with theuser device comprises at least one of: a name of a user of the userdevice, an age of the user of the user device, a gender of the user ofthe user device, an address of the user of the user device, one or moreemergency contacts of the user of the user device, or one or more namesof relatives of the user of the user device.
 33. The method of claim 32,wherein the one or more parameters of the subscriber informationassociated with the user device comprises the one or more emergencycontacts of the user of the user device, and the method furthercomprises: transmitting a request for sharing location to one or moreother devices associated with the one or more emergency contacts of theuser of the user device; receiving locations of the one or more otherdevices associated with the one or more emergency contacts of the userof the user device; determining at least one other device from the oneor more other devices in a proximity to the user device based on acomparison of the locations of the one or more other devices and thecurrent location information of the user device; and transmitting, tothe at least one other device, an emergency notification comprising thecurrent location information of the user device.
 34. The method of claim27, wherein the user device is attached to an eNodeB on a non-accessnetwork channel.
 35. The method of claim 27, wherein determining thecurrent location information of the user device is based on at least oneof: an assisted Global Positioning System (GPS), an observed timedifference of arrival, or an enhanced cell ID.
 36. A system for routinga call, the system comprising: a memory storing a set of instructions;and one or more processors configured to execute the set of instructionsto cause the system to perform: receiving, from a user device, a call;determining a current location information of the user device based onthe call; identifying a Public-Safety Answering Point (PSAP)corresponding to the current location information of the user device;and routing the call to the identified PSAP.
 37. The system of claim 36,wherein identifying the PSAP corresponding to the current locationinformation of the user device further comprises: identifying a servingcell identifier for the user device based on the current locationinformation of the user device; and selecting, in a cell site masterdatabase, the PSAP associated with the identified serving cellidentifier.
 38. The system of claim 37, wherein the one or moreprocessors are further configured to execute the set of instructions tocause the system to perform: obtaining, from a subscriber informationdatabase, one or more parameters of subscriber information associatedwith the user device; and transmitting, to the PSAP, the currentlocation information and the one or more parameters of the subscriberinformation.
 39. The system of claim 38, wherein the one or moreprocessors are further configured to execute the set of instructions tocause the system to perform: receiving, from the PSAP, a locationrequest for the user device; redetermining the current locationinformation of the user device; obtaining, from the subscriberinformation database, one or more additional parameters of thesubscriber information associated with the user device; andtransmitting, to the PSAP, redetermined current location information andthe one or more additional parameters.
 40. The system of claim 37,wherein the cell site master database comprises a correlation of aplurality of cell identifiers with one or more cities and one or morePSAPs, and selecting the PSAP associated with the identified servingcell identifier further comprises: identifying a serving city based on acomparison of the identified serving cell identifier with the pluralityof cell identifiers; and determining the PSAP that is associated withthe identified serving city.
 41. The system of claim 36, wherein the oneor more parameters of the subscriber information associated with theuser device comprises at least one of: a name of a user of the userdevice, an age of the user of the user device, a gender of the user ofthe user device, an address of the user of the user device, one or moreemergency contacts of the user of the user device, or one or more namesof relatives of the user of the user device.
 42. The system of claim 41,wherein the one or more parameters of the subscriber informationassociated with the user device comprises the one or more emergencycontacts of the user of the user device, and the one or more processorsare further configured to execute the set of instructions to cause thesystem to perform: transmitting a request for sharing location to one ormore other devices associated with the one or more emergency contacts ofthe user of the user device; receiving locations of the one or moreother devices associated with the one or more emergency contacts of theuser of the user device; determining at least one other device from theone or more other devices in a proximity to the user device based on acomparison of the locations of the one or more other devices and thecurrent location information of the user device; and transmitting, tothe at least one other device, an emergency notification comprising thecurrent location information of the user device.
 43. The system of claim36, wherein the user device is attached to an eNodeB on a non-accessnetwork channel.
 44. The system of claim 36, wherein determining thecurrent location information of the user device is based on at least oneof: an assisted Global Positioning System (GPS), an observed timedifference of arrival, or an enhanced cell ID.
 45. The system of claim36, wherein the system is a serving TSP network system that receives thecall via an eNodeB.
 46. A non-transitory computer readable medium thatstores a set of instructions that is executable by one or moreprocessors of a computer system to cause the computer system to performa method for routing a call, the method comprising: receiving, from auser device, a call; determining a current location information of theuser device based on the call; identifying a Public-Safety AnsweringPoint (PSAP) corresponding to the current location information of theuser device; and routing the call to the identified PSAP.